Hypervisor for access points and edge nodes

ABSTRACT

Systems and methods include a hypervisor for access points, edge nodes, and other network elements to facilitate use of and compatibility with shared access systems.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to, and is a continuation of,copending U.S. patent application Ser. No. 15/445,209, filed Feb. 28,2017, the entirety of which is incorporated herein by reference in itsentirety.

TECHNICAL FIELD

This disclosure relates generally to network management and, morespecifically, to assigning and configuring networks and network elementsto support shared access systems.

BACKGROUND

Certain regulating bodies, such as national governments, regulate theuse of various signal frequencies and blocks of frequencies asspectrums. However, as use of wireless communication techniquescontinues to grow, efficient utilization of spectrums is becomingincreasingly important to provide a sufficient spectrum of frequenciesto support the general public.

Some regulated spectrums of frequencies are (or were at one time)dedicated specifically for governmental use only. For example, somefrequencies are reserved or restricted for use by governmental users forapplications such as radar, radios, et cetera. However, in order tomaximize spectrum utilization, some of these spectrums may beconditionally available to non-regulated users.

Accordingly, systems are needed to observe and support the regulatedsystems, which will be provide interoperability with legacy connectivitysystems.

SUMMARY

In embodiments, a system comprises an access point communication moduleconfigured to communicate with two or more access points and a sharedaccess communication module configured to communicate with a networkelement configured to provide changes to shared access system data tothe access point communication module. The system further comprises alogging module that creates a log including the changes to the sharedaccess system data and a shared access processing module configured totransmit, to at least one access point of the two or more access points,an access point command based on the changes to the shared access systemdata in response to determining that the at least one access point isimpacted by the changes to the shared access system data based on thechanges to the shared access system data and operating parameters of theat least one access point.

In embodiments, a method comprises receiving changes to shared accesssystem data from a network element at an access point shared accesssystem manager in communication with two or more access points, thenetwork element in communication with a shared access system element.The method further comprises creating a log including the changes to theshared access system data and determining that at least one access pointamong the two or more access points is impacted by the changes to theshared access system data based on the changes to the shared accesssystem data and operating parameters of the at least one access point.The method further comprises modifying, in response to determining thatthe at least one access point is impacted by the changes, the at leastone access point in accordance with the changes.

In embodiments, a system comprises a computer-readable medium storinginstructions. The instructions, when executed by a processor, effectuateoperations comprising receiving changes to shared access system data,creating a log including changes in the changes to the shared accesssystem data, determining at least one access point among two or moreaccess points is impacted by the changes, and generating, in response todetermining that the at least one access point is impacted by thechanges to the shared access system data, an access point command basedon the changes to the shared access system data, as well as transmittingthe access point command to the at least one access point.

These and other embodiments are described in greater detail elsewhereherein.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide an understanding ofthe variations in implementing the disclosed technology. However, theinstant disclosure may take many different forms and should not beconstrued as limited to the examples set forth herein. Where practical,like numbers refer to like elements throughout.

FIG. 1A illustrates a block diagram of an example network employingaspects of the disclosure herein.

FIG. 1B illustrates a block diagram of an example access pointhypervisor utilized with the network of FIG. 1A and other aspectsherein.

FIG. 2 illustrates a block diagram of an example methodology utilizingan access point hypervisor disclosed herein.

FIG. 3 is a representation of an example network.

FIG. 4 depicts an example communication system that provides wirelesstelecommunication services over wireless communication networks.

FIG. 5 depicts an example communication system that provides wirelesstelecommunication services over wireless communication networks.

FIG. 6 is a diagram of an example telecommunications system in which thedisclosed methods and processes may be implemented.

FIG. 7 is an example system diagram of a radio access network and a corenetwork.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network.

FIG. 9 illustrates an example architecture of a GPRS network.

FIG. 10 is a block diagram of an example public land mobile network(PLMN).

DETAILED DESCRIPTION

Aspects herein are directed to a hypervisor for managing edge nodes andaccess points, such as eNodeBs, in conjunction with shared accesssystems for conditional use of regulated frequency spectrums. WhileeNodeBs are most frequently discussed as examples of access pointsthroughout herein, it is understood that other access points, edgenodes, base station transceivers, et cetera, which can but need not bepartly or wholly virtualized, can be used in conjunction with aspectsherein. Further, while aspects herein may be described as a“hypervisor,” it is understood various alternative management elementsfor managing virtual or physical network elements can be utilizedwithout departing from the scope or spirit of the innovation.

An eNodeB, or E-UTRAN (Evolved UMTS (Universal Mobile TelecommunicationsSystem) Terrestrial Radio Access Network) Node B is an element inwireless networks that communicates directly with mobile devicesconnecting to a wireless network. Current eNodeBs and other accesspoints for wireless connectivity operate in assigned frequencieslicensed to carrier operators. These access points are typicallyprovided as dedicated hardware running software for facilitatingconnections and operation of user equipment to carrier networks. Theconnection between user equipment and the access point is wireless, andthe connection between the access point and core network is typicallycarried using high speed lines (e.g., fiber, 100 Gigabit Ethernet, etcetera).

Assigned frequencies are not an indefinite and immovable arrangement,and access points will operate only partially in pre-assigned andfull-time licensed frequencies. Future wireless radio access networkinterfaces will include “shared spectrum.” Governmental entities areexpected to allow some or all of spectrums currently dedicated tomilitary incumbents to new users. However, the military may stillrequire exclusive use of these spectrums or portions thereof to maintainsecurity and operational feasibility. Therefore, sharing may becontingent upon a variety of conditions, such as allowing access tonon-utilized portions of a spectrum or limiting use to particular times.

Moving toward such shared spectrum solutions, in 2015 the FederalCommunications Commission (FCC) published an order making available 150MHz of spectrum in the 3.5 Ghz band. However, the FCC stipulated thatthe only way that his spectrum could be used would be with a SharedAccess System (or “SAS”) implementation technologies. Thus the FCCenvisioned a shared access system that would inform carriers and generalusers of frequency changes in response to military incumbent'srequirements. The SAS may receive this information from, e.g.,Environmental Sensing Capabilities or Spectrum Resource Managers orvarious other sources (such as a third-party or military-run sharedaccess system element of a network).

To support shared spectrum, eNodeBs and other access points will beresponsive to changes in available frequencies. Access points willsupport licensed frequencies and as well as conditionally support sharedfrequencies according to Shared Access System (SAS) element input. TheSAS elements will communicate a frequency allocation change or otherinformation to the access point (either directly or through interveningnetwork elements) so that the access point can in turn changefrequencies and communicate the new frequency assignment to connecteduser equipment. These access points can be implemented as dedicatedspecialized hardware or software, as individual units or virtualizedinstances allowing multiple access points to run on a single node ordistributed across multiple nodes.

An access point shared spectrum hypervisor can be used to manage theseshared spectrum access points. In embodiments, the hypervisor caninclude or be a virtual machine manager. With respect to managingvirtual machines, the hypervisor permits multiple operating systems toshare a single hardware host. Each operating system may appear to haveits host's processor, memory, and other resources all to itself. Thisdisclosure proposes the use of a hypervisor specifically designed tosupport multiple eNodeBs (or other shared spectrum access points)residing in one processor. The hypervisor may communicate with upstreamnetwork elements (regional network elements, core network elements) orothers communicatively coupled with the SAS elements providing frequencyinformation or other shared access system data to manage associatedaccess points.

While aspects hereafter illustrate example computing environments, it isunderstood that non-standard computing hardware and computer scienceassets are used in conjunction with the innovation. Use of specializedinterfaces to SAS data sources, access points, and various networkelements, coupled with dynamic security filters and firewalls to protectboth the SAS data source(s) and core and regional network elements,means that environment-specific hardware and code will be employed forimplementation of many aspects.

Turning to the drawings, FIG. 1A illustrates example system 100 forconnecting users to network 150 in accordance with aspects herein.System 100 as illustrated includes a plurality of user equipment 198,196, 194, which can connect to one of a plurality of access points 188and 186. Access points 188 provide connectivity to one of plurality ofregional networks 180 and 182, or in alternative or complementaryembodiments may connected directly to core network 178. Regionalnetworks 180 and 182 connect to core network 178. Core network 178 canprovide connectivity to network 150, which can be the Internet or othernetworks outside the carrier network of core network 178. In alternativeor complementary embodiments, some of plurality of regional networks 180and 182 can also connect to non-carrier networks.

Core network 178 includes a variety of network elements such as mobilitymanagement entity 176, home subscriber server 174, authentication,authorization, and accounting server 172, various gateways 170 (forproviding connectivity and services as well as network administration),and a variety of additional elements 168 to provide core networkenvironment functionality or proprietary capabilities. Similar networkelements may also exist in, e.g., regional network(s) 180.

In system 100, elements are configured to support shared accessfrequency functionality. In this regard, access point shared accesssystem hypervisor 110 is provided for management and monitoring ofaccess points 188 and 186. While access point shared access systemhypervisor 110 is shown downstream of regional network 180 and upstreamof access points 188 and 186, it is understood that access point sharedaccess system hypervisor 110 may be hosted in a variety of physical orlogical locations and need not be implemented as illustrated. In anembodiment, one or more of access points 188 and 186 is hosted in or byaccess point shared access system hypervisor 110, and thus theseelements may be illustrated alternatively or complementarily in commonblocks of a block diagram or elsewhere. In embodiments, two or moreaccess point shared access system hypervisors 110 can exist in system100.

Access point shared access system hypervisor 110 can receive a varietyof inputs in managing portions of system 100 including access points 188and 186. In the embodiment illustrated, shared access system elements140 and sensor module 142 exist outside core network 178 but caninteract with, e.g., elements of core network 178 (or, alternatively,regional network 180) to provide shared access system data and allowaccess point shared access system hypervisor 110 to manage at leastaccess points 188 and 186 based on information received from sharedaccess system elements 140. Shared access system elements can be anynumber of systems or network elements for facilitating shared spectrumby providing usage requirements or scheduling related to shared spectrumfrequencies, or sensing frequency usage by priority incumbents.

FIG. 1B illustrates a more particularized view of access point sharedaccess system hypervisor 110. Access point shared access systemhypervisor 110 is communicatively coupled to regional network 180 and/orcore network 178, from which it can receive shared access system data(including, but not limited to, frequency usage or changes within ashared spectrum). By routing shared access system data—which is receivedfrom elements outside the carrier network—through core network 178and/or regional network 180, security can be preserved by shieldingaccess point shared access system hypervisor 110, access points 188 and186 (e.g., eNodeBs), and user equipment 198, 196, and 194 from externalentities, and vice versa.

Access point shared access system hypervisor 110 can include a sharedaccess communication module 112, a shared access processing module 114,an access point communication module 116, and, in embodiments,additional modules 118. Communication to core network 178 and/orregional network 180, or portions thereof concerning the transmissionand reception of shared access system data, can be handled by sharedaccess communication module 112. In particular, shared accesscommunication module 112 can communicate with a core or regional networkelement that is configured to receive shared access system data andprovide the shared access system data to shared access communicationmodule 112. As discussed, the shared access system data includes, but isnot limited to, shared access system frequency change information.

Shared access processing module 114 thereafter generates an access pointcommand by analyzing the shared access system data, the access pointcommand transmitted to the access point. Analysis of the shared accesssystem data can include interpretation, application of rules, discerningor translating instructions, et cetera, to facilitate use by elementscommunicatively coupled to shared access processing module 114. Theaccess point command can include, but is not limited to, instructionsfor one or more of changing an access point frequency, assigning orremoving resources for the access point, and handing over user equipmentto a different access point.

In embodiments, the access points (e.g., access points 186 or 188) are avirtualized access point instance. As such, access points 186 or 188 canbe created, destroyed, or modified on demand. In embodiments, the accesspoint command includes instructions for creating or destroying thevirtualized access point instance. Nonetheless, in complementaryembodiments, the access point shared access system hypervisor isinteroperable with additional non-virtualized access points (e.g.,legacy access points).

In embodiments, shared access processing module 114 or other elements ofaccess point shared access system hypervisor 110 can determine one ormore access points among access points 186 and 188 that are impacted bythe shared access system data. This can include requirements forconfiguration changes including, but not limited to, frequencies onwhich the access point transmits or receives based on the shared accesssystem data.

Access point communication module 116 can transmit information fromaccess point shared access system hypervisor 110, including but notlimited to the access point command, to one or more access points.Information provided using access point communication module 116 can betransmitted selectively to identified access points 186 and 188, orpassed to all connected access points to allow access points 186 and 188to determine if they are impacted or how to handle the information.

In embodiments, additional modules 118 can facilitate logging. Forexample, access point shared access system hypervisor 110 can create alog including changes in the shared access system data. In embodiments,access point shared access system hypervisor further analyzes the log toproduce a change trend, the access point shared access system hypervisorfurther predicts a subsequent change in the shared access system databased at least in part on the change trend. Network conditions orcontextual information such as traffic, time of day or date,maintenance, et cetera, can be factored into this analysis as well.

In embodiments, additional modules 118 can include a configurationengine of access point shared access system hypervisor 110. Theconfiguration engine can configure the access point. This can include,e.g., setting security of the access point.

In embodiments, additional modules 118 can include a usage engine thattracks a capacity and/or usage of one or more access points. Thisinformation can be used for, e.g., creation or destruction ofvirtualized instances to manage capacity or achieve desired utilizationmetrics.

In embodiments, additional modules 118 can include various interfaces.Interfaces of access point shared access system hypervisor 110 caninclude an interface to one or more of an antenna, a radio head, and aconnectivity element. Connectivity elements can include, e.g., a smartintegrated access device (SIAD).

FIG. 2 illustrates a block diagram of an example methodology 200 formanaging access points and other network elements using shared accesssystem data. Methodology 200 begins at 202 and proceeds to 204 whereshared access system data is received at an access point shared accesssystem hypervisor. This shared access system data can be received from,e.g., one or more regional or core network elements communicativelycoupled with shared access system elements.

At 206 a determination can be made as to whether the shared accesssystem data has changed. Changes can include, e.g., current or projecteduse of shared spectrum frequencies, current or projected availability ofshared spectrum frequencies, and others. If the shared access system hasnot changed as indicated by the determination at 206 returning negative,methodology 200 can recycle to 204 where additional shared access systemdata is received or awaited to manage shared access system frequenciesthroughout core or regional networks.

If the determination at 206 returns positive, methodology 200 proceedsto 208 where a determination is made as to whether any access points(e.g., eNodeBs) related to the network element hypervisor are impactedby the change. If the determination at 208 returns negative, methodology200 may proceed to end at 216, or alternatively recycle to 204 whereadditional shared access system data is received or awaited to manageshared access system frequencies used by access points within thenetwork.

If the determination at 208 returns positive, an access point command isgenerated at 210. The access point command can at least provide acommand for one or more access points impacted by the change to sharedaccess system data to ensure the access point configuration or operationcomplies with shared access system parameters.

At 212, the network command generated at 210 is transmitted to theaccess points. Thereafter, at 214, in embodiments the access pointcommand is executed to effectuate the intended changes. At 216,methodology 200 ends, or may recycle to 204 to receive or await furthershared access system data.

Methodology 200 is illustrated for ease of understanding but should notbe deemed limiting. Additional aspects can be included, or aspectsexcluded, without departing from the scope or spirit of the innovation.Various other methodologies can be implemented according to thedisclosures herein.

For example, a method can comprise receiving shared access system datafrom a core or regional network element at an access point shared accesssystem hypervisor. The core or regional network element can be incommunication with a shared access system element, and the shared accesssystem data can include changes to available frequency bands in a sharedaccess spectrum. The method can further include generating an accesspoint command by analyzing the shared access system data at the accesspoint shared access system hypervisor and transmitting the access pointcommand to an access point.

In further embodiments, methods can include determining the access pointis impacted (or additional access points that are impacted) by thechanges to the available frequency bands in the shared access spectrum.In embodiments, the access point command instructs a frequency change tocomply with the shared access system data.

In further embodiments, the access point is a virtualized instance of anaccess point. Embodiments of the method can include creating ordestroying the virtualized instance of the access point.

In embodiments, a method can include monitoring capacity and utilizationof the access point.

In embodiments, acknowledgements can be sent from access points tohypervisors to ensure access point commands or other transmissions arereceived and/or executed. In additional embodiments, access points canreport to hypervisors with information received from outside thehypervisor to ensure information is disseminated among the network, andproperly processed and actioned.

Various implementations can utilize a variety of different options fordeploying access points and management entities for access points whichare compliant with shared spectrum technology. In particularembodiments, the access point shared access system hypervisor runs in anarchitecture supporting eNodeB processors and functionality rather thanin a general computing platform. The hypervisor can host or supportexisting access points residing on or embodied in dedicated hardware(e.g., legacy cell tower eNodeB) as well as virtualized instances ofaccess points, allowing interoperability and full support for sharedspectrum. In embodiments, hardware can be developed for performance ofone or more virtualized eNodeBs.

In embodiments, the hypervisor can include specialized interfaces toother hardware components which interact with or support access pointssuch as eNodeBs. For example, interfaces to antennas, radio heads,connectivity elements (e.g., smart integrated access devices (SIADS)),and others can be included in the access point shared access systemhypervisor. The hypervisor can include microcode to facilitatecommunication between SAS elements or other upstream network elementsthrough which SAS elements provide information to eNodeBs.

In an embodiment, when a frequency allocation change is communicated bythe SAS network elements, the hypervisor can determine (e.g., byanalysis, artificial intelligence, data processing) which hosted accesspoints are affected and the manner and timing for communicating andimplementing the frequency change. The hypervisor can also keep of a logof frequency changes for access points which can be used for audit andsecurity purposes. In addition, the hypervisor can analyze previousfrequency allocation changes and predict future changes to the hostedaccess points.

In embodiments, the hypervisor can create virtual instances of accesspoints on demand in order to satisfy capacity constraints or frequencyallocation changes. The hypervisor can include firewalls or othersecurity modules to front-end virtual instances of access points createdor managed.

The hypervisor can interface with core network elements or regionalnetwork elements in contact with SAS elements, thereby providing two-waysecurity from the carrier network on behalf of SAS elements and for thecarrier network against outside entities such as SAS elements. Tointeract with various network elements, the access point shared accesssystem hypervisor can include specialized application programminginterfaces (APIs) or API commands, which can be within the access pointshared access system hypervisor to allow other entities to query itsinformation, or be in other network elements with compatible queries orcommands included within the hypervisor.

The hypervisor can enable remote configuration and security of accesspoints hosted or managed by the hypervisor. User equipment switching orhandover between access points can be handled, managed, or forced by thehypervisor. This can be based on various constraints related to theaccess points, shared access system data, et cetera. The hypervisor caninclude a tracking module to monitor access points it hosts or manages,monitoring, e.g., capacity and utilization of its access points.

FIGS. 3-10 show a variety of aspects used in conjunction with orproviding context for the hypervisor and other elements. Particularly,FIG. 3 describes virtualization in the context of instances describedabove, and FIGS. 4-10 show various computing and network environmentswith which aspects herein are compatible.

FIG. 3 is a representation of an example network 300. Network 300 maycomprise an SDN. Network 300 may include one or more virtualizedfunctions implemented on general purpose hardware, such as in lieu ofhaving dedicated hardware for every network function. General purposehardware of network 300 may be configured to run virtual networkelements to support communication services, such as mobility services,including consumer services and enterprise services. These services maybe provided or measured in sessions.

A virtual network functions (VNFs) 302 may be able to support a limitednumber of sessions. Each VNF 302 may have a VNF type that indicates itsfunctionality or role. For example, FIG. 3 illustrates a gateway VNF 302a and a policy and charging rules function (PCRF) VNF 302 b.Additionally or alternatively, VNFs 302 may include other types of VNFs.Each VNF 302 may use one or more virtual machines (VMs) 304 to operate.Each VM 304 may have a VM type that indicates its functionality or role.For example, FIG. 3 illustrates a MCM VM 304 a, an ASM VM 304 b, and aDEP VM 304 c. Additionally or alternatively, VMs 304 may include othertypes of VMs. Each VM 304 may consume various network resources from ahardware platform 306, such as a resource 308, a virtual centralprocessing unit (vCPU) 308 a, memory 308 b, or a network interface card(NIC) 308 c. Additionally or alternatively, hardware platform 306 mayinclude other types of resources 308.

While FIG. 3 illustrates resources 308 as collectively contained inhardware platform 306, the configuration of hardware platform 306 mayisolate, for example, certain memory 308 c from other memory 108 c.

Hardware platform 306 may comprise one or more chasses 310. Chassis 310may refer to the physical housing or platform for multiple servers orother network equipment. In an aspect, chassis 310 may also refer to theunderlying network equipment. Chassis 310 may include one or moreservers 312. Server 312 may comprise general purpose computer hardwareor a computer. In an aspect, chassis 310 may comprise a metal rack, andservers 312 of chassis 310 may comprise blade servers that arephysically mounted in or on chassis 310.

Each server 312 may include one or more network resources 308, asillustrated. Servers 312 may be communicatively coupled together (notshown) in any combination or arrangement. For example, all servers 312within a given chassis 310 may be communicatively coupled. As anotherexample, servers 312 in different chasses 310 may be communicativelycoupled. Additionally or alternatively, chasses 310 may becommunicatively coupled together (not shown) in any combination orarrangement.

The characteristics of each chassis 310 and each server 312 may differ.The type or number of resources 310 within each server 312 may vary. Inan aspect, chassis 310 may be used to group servers 312 with the sameresource characteristics. In another aspect, servers 312 within the samechassis 310 may have different resource characteristics.

Given hardware platform 306, the number of sessions that may beinstantiated may vary depending upon how efficiently resources 308 areassigned to different VMs 304. For example, assignment of VMs 304 toparticular resources 308 may be constrained by one or more rules. Forexample, a first rule may require that resources 308 assigned to aparticular VM 304 be on the same server 312 or set of servers 312. Forexample, if VM 304 uses eight vCPUs 308 a, 1 GB of memory 308 b, and 2NICs 308 c, the rules may require that all of these resources 308 besourced from the same server 312. Additionally or alternatively, VM 304may require splitting resources 308 among multiple servers 312, but suchsplitting may need to conform with certain restrictions. For example,resources 308 for VM 304 may be able to be split between two servers312. Default rules may apply. For example, a default rule may requirethat all resources 308 for a given VM 304 must come from the same server312.

An affinity rule may restrict assignment of resources 308 for aparticular VM 304 (or a particular type of VM 304). For example, anaffinity rule may require that certain VMs 304 be instantiated on (e.g.,consume resources from) the same server 312 or chassis 310. For example,if VNF 302 uses six MCM VMs 304 a, an affinity rule may dictate thatthose six MCM VMs 304 a be instantiated on the same server 312 (orchassis 310). As another example, if VNF 302 uses MCM VMs 304 a, ASM VMs304 b, and a third type of VMs 304, an affinity rule may dictate that atleast the MCM VMs 304 a and the ASM VMs 304 b be instantiated on thesame server 312 (or chassis 310). Affinity rules may restrict assignmentof resources 308 based on the identity or type of resource 308, VNF 302,VM 304, chassis 310, server 312, or any combination thereof.

An anti-affinity rule may restrict assignment of resources 308 for aparticular VM 304 (or a particular type of VM 304). In contrast to anaffinity rule—which may require that certain VMs 304 be instantiated onthe same server 312 or chassis 310—an anti-affinity rule requires thatcertain VMs 304 be instantiated on different servers 312 (or differentchasses 310). For example, an anti-affinity rule may require that MCM VM304 a be instantiated on a particular server 312 that does not containany ASM VMs 304 b. As another example, an anti-affinity rule may requirethat MCM VMs 304 a for a first VNF 302 be instantiated on a differentserver 312 (or chassis 310) than MCM VMs 304 a for a second VNF 302.Anti-affinity rules may restrict assignment of resources 308 based onthe identity or type of resource 308, VNF 302, VM 304, chassis 310,server 312, or any combination thereof.

Within these constraints, resources 308 of hardware platform 306 may beassigned to be used to instantiate VMs 304, which in turn may be used toinstantiate VNFs 302, which in turn may be used to establish sessions.The different combinations for how such resources 308 may be assignedmay vary in complexity and efficiency. For example, differentassignments may have different limits of the number of sessions that canbe established given a particular hardware platform 306.

For example, consider a session that may require gateway VNF 302 a andPCRF VNF 302 b. Gateway VNF 302 a may require five VMs 304 instantiatedon the same server 312, and PCRF VNF 302 b may require two VMs 304instantiated on the same server 312. (Assume, for this example, that noaffinity or anti-affinity rules restrict whether VMs 304 for PCRF VNF302 b may or must be instantiated on the same or different server 312than VMs 304 for gateway VNF 302 a.) In this example, each of twoservers 312 may have sufficient resources 308 to support 10 VMs 304. Toimplement sessions using these two servers 312, first server 312 may beinstantiated with 10 VMs 304 to support two instantiations of gatewayVNF 302 a, and second server 312 may be instantiated with 9 VMs: fiveVMs 304 to support one instantiation of gateway VNF 302 a and four VMs304 to support two instantiations of PCRF VNF 302 b. This may leave theremaining resources 308 that could have supported the tenth VM 304 onsecond server 312 unused (and unusable for an instantiation of either agateway VNF 302 a or a PCRF VNF 302 b). Alternatively, first server 312may be instantiated with 10 VMs 304 for two instantiations of gatewayVNF 302 a and second server 312 may be instantiated with 10 VMs 304 forfive instantiations of PCRF VNF 302 b, using all available resources 308to maximize the number of VMs 304 instantiated.

Consider, further, how many sessions each gateway VNF 302 a and eachPCRF VNF 302 b may support. This may factor into which assignment ofresources 308 is more efficient. For example, consider if each gatewayVNF 302 a supports two million sessions, and if each PCRF VNF 302 bsupports three million sessions. For the first configuration—three totalgateway VNFs 302 a (which satisfy the gateway requirement for sixmillion sessions) and two total PCRF VNFs 302 b (which satisfy the PCRFrequirement for six million sessions)—would support a total of sixmillion sessions. For the second configuration-τwo total gateway VNFs302 a (which satisfy the gateway requirement for four million sessions)and five total PCRF VNFs 302 b (which satisfy the PCRF requirement for15 million sessions)—would support a total of four million sessions.Thus, while the first configuration may seem less efficient looking onlyat the number of available resources 308 used (as resources 308 for thetenth possible VM 304 are unused), the second configuration is actuallymore efficient from the perspective of being the configuration that cansupport more the greater number of sessions.

To solve the problem of determining a capacity (or, number of sessions)that can be supported by a given hardware platform 305, a givenrequirement for VNFs 302 to support a session, a capacity for the numberof sessions each VNF 302 (e.g., of a certain type) can support, a givenrequirement for VMs 304 for each VNF 302 (e.g., of a certain type), agiven requirement for resources 308 to support each VM 304 (e.g., of acertain type), rules dictating the assignment of resources 308 to one ormore VMs 304 (e.g., affinity and anti-affinity rules), the chasses 310and servers 312 of hardware platform 306, and the individual resources308 of each chassis 310 or server 312 (e.g., of a certain type), aninteger programming problem may be formulated.

First, a plurality of index sets may be established. For example, indexset L may include the set of chasses 310. For example, if a systemallows up to 6 chasses 310, this set may be:

-   -   L={1, 2, 3, 4, 5, 6},    -   where l is an element of L.

Another index set J may include the set of servers 312. For example, ifa system allows up to 16 servers 312 per chassis 310, this set may be:

-   -   J={1, 2, 3, . . . , 16},    -   where j is an element of J.

As another example, index set K having at least one element k mayinclude the set of VNFs 302 that may be considered. For example, thisindex set may include all types of VNFs 302 that may be used toinstantiate a service. For example, let

-   -   K={GW, PCRF}    -   where GW represents gateway VNFs 302 a and PCRF represents PCRF        VNFs 302 b.

Another index set I(k) may equal the set of VMs 304 for a VNF 302 k.Thus, let

-   -   I(GW)={MCM, ASM, IOM, WSM, CCM, DCM}    -   represent VMs 304 for gateway VNF 302 a, where MCM represents        MCM VM 304 a, ASM represents ASM VM 304 b, and each of IOM, WSM,        CCM, and DCM represents a respective type of VM 304. Further,        let    -   I(PCRF)={DEP, DIR, POL, SES, MAN}    -   represent VMs 304 for PCRF VNF 302 b, where DEP represents DEP        VM 304 c and each of DIR, POL, SES, and MAN represent a        respective type of VM 304.

Another index set V may include the set of possible instances of a givenVM 304. For example, if a system allows up to 20 instances of VMs 302,this set may be:

-   -   V={1, 2, 3, . . . , 20},    -   where v is an element of V.

In addition to the sets, the integer programming problem may includeadditional data. The characteristics of VNFs 302, VMs 304, chasses 310,or servers 312 may be factored into the problem. This data may bereferred to as parameters. For example, for given VNF 302 k, the numberof sessions that VNF 302 k can support may be defined as a functionS(k). In an aspect, for an element k of set K, this parameter may berepresented by S(k)>=0;

is a measurement of the number of sessions k can support. Returning tothe earlier example where gateway VNF 302 a may support 2 millionsessions, then this parameter may be S(GW)=2,000,000.

VM 304 modularity may be another parameter in the integer programmingproblem. VM 304 modularity may represent the VM 304 requirement for atype of VNF 302. For example, for k that is an element of set K and ithat is an element of set I, each instance of VNF k may require M(k, i)instances of VMs 304. For example, recall the example where

I(GW)={MCM, ASM, IOM, WSM, CCM, DCM}.

In an example, M(GW, I(GW)) may be the set that indicates the number ofeach type of VM 304 that may be required to instantiate gateway VNF 302a. For example,

M(GW, I(GW))={2, 16, 4, 4, 2, 4}

may indicate that one instantiation of gateway VNF 302 a may require twoinstantiations of MCM VMs 304 a, 16 instantiations of ACM VM 304 b, fourinstantiations of IOM VM 304, four instantiations of WSM VM 304, twoinstantiations of CCM VM 304, and four instantiations of DCM VM 304.

Another parameter may indicate the capacity of hardware platform 306.For example, a parameter C may indicate the number of vCPUs 308 arequired for each VM 304 type i and for each VNF 302 type k. Forexample, this may include the parameter C(k, i).

For example, if MCM VM 304 a for gateway VNF 302 a requires 20 vCPUs 308a, this may be represented as

C(GW, MCM)=20.

However, given the complexity of the integer programming problem—thenumerous variables and restrictions that must be satisfied—implementingan algorithm that may be used to solve the integer programming problemefficiently, without sacrificing optimality, may be difficult.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be at least partiallyimplemented as an SDN. Network architecture 400 disclosed herein isreferred to as a modified LTE-EPS architecture 400 to distinguish itfrom a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. LTE-EPS network architecture400 may include an access network 402, a core network 404, e.g., an EPCor Common BackBone (CBB) and one or more external networks 406,sometimes referred to as PDN or peer entities. Different externalnetworks 406 can be distinguished from each other by a respectivenetwork identifier, e.g., a label according to DNS naming conventionsdescribing an access point to the PDN. Such labels can be referred to asAccess Point Names (APN). External networks 406 can include one or moretrusted and non-trusted external networks such as an internet protocol(IP) network 408, an IP multimedia subsystem (IMS) network 410, andother networks 412, such as a service network, a corporate network, orthe like. In an aspect, access network 402, core network 404, orexternal network 405 may include or communicate with a network.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from a peer entity, andtriggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, HSS 422 can store information such as authorization ofthe user, security requirements for the user, quality of service (QoS)requirements for the user, etc. HSS 422 can also hold information aboutexternal networks 406 to which the user can connect, e.g., in the formof an APN of external networks 406. For example, MME 418 can communicatewith HSS 422 to determine if UE 414 is authorized to establish a call,e.g., a voice over IP (VoIP) call before the call is established.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively, or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of a network herein,e.g., by one or more of tunnel endpoint identifiers, an IP address and auser datagram protocol port number. Within a particular tunnelconnection, payloads, e.g., packet data, which may or may not includeprotocol related information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an example diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as a processor, UE 414, eNB 416, MME 418, SGW 420,HSS 422, PCRF 424, PGW 426 and other devices described herein. In someembodiments, the machine may be connected (e.g., using a network 502) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client user machine in a server-clientuser network environment, or as a peer machine in a peer-to-peer (ordistributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise a mobile device, a network device, or the like, or anycombination thereof. By way of example, WTRUs 602 may be configured totransmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 100 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., a mobiledevice, a mobile positioning center, a network device, a detecteddevice, or the like, or any combination thereof). Radio access network904 comprises a plurality of BSSs such as BSS 912, which includes a BTS914 and a BSC 916. Core network 906 may include a host of variousnetwork elements. As illustrated in FIG. 9, core network 906 maycomprise MSC 918, service control point (SCP) 920, gateway MSC (GMSC)922, SGSN 924, home location register (HLR) 926, authentication center(AuC) 928, domain name system (DNS) server 930, and GGSN 932.Interconnect network 908 may also comprise a host of various networks orother network elements. As illustrated in FIG. 9, interconnect network908 comprises a PSTN 934, an FES/Internet 936, a firewall 1038, or acorporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, a network device or other electronic system, orany combination thereof may serve as MS 1002. MS 1002 may be one of, butnot limited to, a cellular telephone, a cellular telephone incombination with another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software defined network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life-especially for simple M2M devices-throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes a device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes a device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

What is claimed is:
 1. A system, comprising: an access pointcommunication module configured to communicate with a plurality ofaccess points, wherein each of the plurality of access points isconfigured to communicate with one or more user devices; a shared accesscommunication module configured to communicate with a radio accessnetwork element, a shared access processing module, and the access pointcommunication module, wherein the radio access network element isconfigurable to operate on a carrier frequency and a different frequencyassociated with a shared spectrum, wherein the shared accesscommunication module is configured to provide shared access system datacomprising spectrum frequency changes between the carrier frequency andthe different frequency to the access point communication module,wherein the system is further configured to generate a change trend inthe shared access system data according to analysis of a log of theshared access system data, to predict future changes to the sharedaccess system data according to the change trend, and to track acapacity and a utilization of at least one access point of the pluralityof access points, wherein the change trend to the shared access systemdata describes dedicated resources made conditionally available when notutilized by an incumbent user, wherein the shared access processingmodule is in communication with the access point communication moduleand is configured to transmit, through the access point communicationmodule to the at least one access point of the plurality of accesspoints, an access point command based on the shared access system datain response to determining that the at least one access point isimpacted by the change trend in the shared access system data and thefuture changes to the shared access system data based on operatingparameters of the at least one access point and based on availablefrequency bands, wherein the at least one access point is a virtualizedaccess point instance, wherein the access point command comprisesinstructions for destroying the virtualized access point instance andcreating another virtualized access point based on the change trend inthe shared access system data, and wherein the virtualized access pointinstance is configured to operate based on the change trend in theshared access system data.
 2. The system of claim 1, wherein theanalysis of a log of the shared access system data can include analyzingnetwork conditions, contextual information, or a combination thereof. 3.The system of claim 2, wherein the contextual information can includenetwork traffic, time of day, maintenance, or any combination thereof.4. The system of claim 1, wherein the access point command furtherinstructs a frequency change to comply with the shared access systemdata.
 5. A method, comprising: receiving changes to shared access systemdata from a radio access network element by an access pointcommunication module in communication with a plurality of access points,wherein each of the plurality of access points is configured tocommunicate with one or more user devices, wherein the radio accessnetwork element is in communication with a shared access communicationmodule, wherein the changes to the shared access system data comprisespectrum frequency changes between a carrier frequency and a differentfrequency associated with a shared access spectrum, and wherein thechanges comprise switching between the carrier frequency and thedifferent frequency; receiving, by the access point communicationmodule, future changes to the shared access system data, wherein thefuture changes are predicted based on a change trend in the sharedaccess system data generated based on analysis of a log of the sharedaccess system data, wherein the change trend describes dedicatedresources made conditionally available when not utilized by an incumbentuser; tracking, by the access point communication module, capacity andutilization of at least one access point of the plurality of accesspoints; determining, by the access point communication module, that atleast one access point of the plurality of access points is impacted bythe change trend in the shared access system data and the future changesto the shared access system data based on operating parameters of the atleast one access point and based on available frequency bands; and inresponse to determining that the at least one access point is impactedby the change trend and the future changes to the shared access systemdata, modifying, by the access point communication module, the at leastone access point via an access point command, wherein the at least oneaccess point is a virtualized access point instance, wherein the accesspoint command comprises instructions for destroying the virtualizedaccess point instance and creating another virtualized access pointbased on the change trend in the shared access system data, and whereinthe virtualized access point instance is configured to operate based onthe change trend in the shared access system data.
 6. The method ofclaim 5, wherein the analysis of a log of the shared access system datacan include analyzing network conditions.
 7. The method of claim 6,wherein the analysis of a log of the shared access system data caninclude analyzing contextual information.
 8. The method of claim 7,wherein the contextual information can include network traffic.
 9. Themethod of claim 7, wherein the contextual information can include timeof day.
 10. The method of claim 7, wherein the contextual informationcan include maintenance information.
 11. A system, comprising anon-transitory computer-readable medium storing instructions that whenexecuted by a processor effectuate operations comprising: receivingchanges to shared access system data from a radio access network elementby an access point communication module in communication with aplurality of access points, wherein each of the plurality of accesspoints is configured to communicate with one or more user devices,wherein the radio access network element is in communication with ashared access communication module, wherein the shared access systemdata comprises spectrum frequency changes between a carrier frequencyand a different frequency associated with a shared access spectrum andthe changes comprise switching between the carrier frequency and thedifferent frequency; receiving future changes to the shared accesssystem data, wherein the future changes are predicted based on a changetrend in the shared access system data generated based on analysis of alog of the shared access system data, wherein the change trend describesdedicated resources made conditionally available when not utilized by anincumbent user; tracking capacity and utilization of at least one accesspoint of the plurality of access points; determining that the at leastone access point of the plurality of access points is impacted by thechange trend in the shared access system data and the future changes tothe shared access system data based on available frequency bands; inresponse to determining that the at least one access point is impactedby the change trend and the future changes to the shared access systemdata, generating an access point command based on the change trend inthe shared access system data; and transmitting the access point commandto the at least one access point, wherein the at least one access pointis a virtualized access point instance, wherein the access point commandcomprises instructions for destroying the virtualized access pointinstance and creating another virtualized access point based on thechange trend in the shared access system data, and wherein thevirtualized access point instance is configured to operate based on thechange trend in the shared access system data.
 12. The system of claim11, wherein the analysis of a log of the shared access system data caninclude analyzing network conditions.
 13. The system of claim 12,wherein the analysis of a log of the shared access system data caninclude analyzing contextual information.
 14. The system of claim 13,wherein the contextual information can include network traffic.
 15. Thesystem of claim 13, wherein the contextual information can include timeof day.
 16. The system of claim 11, wherein the operations furthercomprise: providing an interface to one or more of a non-virtualizedaccess point, an antenna, a radio head, and a connectivity element. 17.The system of claim 13, wherein the contextual information can includemaintenance information.